COMPX375-19B (TGA)

Information Systems Industry Project

15 Points

Edit Header Content
Division of Health Engineering Computing & Science
School of Computing and Mathematical Sciences
Department of Computer Science

Staff

Edit Staff Content

Convenor(s)

Lecturer(s)

Jessica Turner

Jessica Turner
3585
G.1.21
To be advised
jessica.turner@waikato.ac.nz

Administrator(s)

Placement Coordinator(s)

Tutor(s)

Student Representative(s)

Lab Technician(s)

Librarian(s)

: debby.dada@waikato.ac.nz

You can contact staff by:

  • Calling +64 7 838 4466 select option 1, then enter the extension.
  • Extensions starting with 4, 5, 9 or 3 can also be direct dialled:
    • For extensions starting with 4: dial +64 7 838 extension.
    • For extensions starting with 5: dial +64 7 858 extension.
    • For extensions starting with 9: dial +64 7 837 extension.
    • For extensions starting with 3: dial +64 7 2620 + the last 3 digits of the extension e.g. 3123 = +64 7 262 0123.
Edit Staff Content

Paper Description

Edit Paper Description Content
In this project-based paper students work in groups to develop an information system. Students are expected to organise themselves into groups of four and find a suitable client and project. Students will submit a series of reports which allow them to develop an information system with a focus on introducing the software development life-cycle in terms of planning, analysis, design, and implementation. At the end of the paper groups should have a working prototype of their information system.
Edit Paper Description Content

Paper Structure

Edit Paper Structure Content

The lecture material presented in this paper does not cover the technical content necessary to develop an information system, it is expected that the students will have the necessary knowledge to complete this aspect of the project from prerequisites or a willingness to gain new skills as required. The lectures will cover the software development life cycle, how to manage a software project in groups, and give necessary knowledge about report writing in order to complete the assessments.

Students are expected to work in groups of four and to self-organise, as a last resort student groups will be formed by the lecturer where necessary. All projects must be approved by the lecturer and you should be able to easily develop the system to a prototype stage within a semester. Students are expected to have the necessary skills and access to the software to create the prototype for the project, that is you should pick technologies that you can easily access.

Tuesday lectures will be used to present lecture material in weeks 1-10. Friday lectures will be used as a group meeting with the lecturer, attendance at these meetings is mandatory and lack of attendance will result in a loss of marks. Students are expected to act professionally with regular attendance, effective group communication and to meet deadlines for the project and associated assessments. Attendance at the presentation session is mandatory, lack of attendance will result in a loss of marks.

Edit Paper Structure Content

Learning Outcomes

Edit Learning Outcomes Content

Students who successfully complete the course should be able to:

  • Apply strategies for working effectively in a group
    Linked to the following assessments:
  • Apply appropriate design and development skills to all phases of the software development cycle
    Linked to the following assessments:
  • Demonstrate practical experience in developing for a real-world client
    Linked to the following assessments:
Edit Learning Outcomes Content
Edit Learning Outcomes Content

Assessment

Edit Assessments Content

Assessment Components

Edit Assessments Content

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0. There is no final exam. The final exam makes up 0% of the overall mark.

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0 or 0:0, whichever is more favourable for the student. The final exam makes up either 0% or 0% of the overall mark.

Component DescriptionDue Date TimePercentage of overall markSubmission MethodCompulsory
1. Memorandum of Understanding
0
  • Online: Submit through Moodle
2. Information System Proposal
15
  • Online: Submit through Moodle
3. Structured Requirements report
15
  • Online: Submit through Moodle
4. Interface Design and Testing Schedule
10
  • Online: Submit through Moodle
5. Database design report
10
  • Online: Submit through Moodle
6. Final Report and Prototype
30
  • Online: Submit through Moodle
7. In-class presentation
10
  • In Class: In Lecture
✔
8. Individual marks for professional behavior
10
Assessment Total:     100    
Failing to complete a compulsory assessment component of a paper will result in an IC grade
Edit Assessments Content

Required and Recommended Readings

Edit Required Readings Content

Recommended Readings

Edit Recommended Readings Content

Lane, D. and Robbins, S. (2011). A Beginner's Guide to the Software Development Life Cycle. In The Chief Information Officer's Body of Knowledge, D. Lane (Ed.). doi:10.1002/9781118269114.ch13

Sides, C.H. How to write and present technical information, Oryx Press, 1991.

Hoffer, J., et al. Modern Systems Analysis and Design. (3rd edition) Prentice-Hall, 2015.

Edit Recommended Readings Content

Online Support

Edit Online Support Content
Additional suggested readings will be posted on Moodle, as will lecture notes (if available), assessment descriptions and rubrics.
Edit Online Support Content

Workload

Edit Workload Content
On average you should expect to spend about 16 hours per week on this class. This figure includes lectures, reading, assignments, meetings, and system development.
Edit Workload Content

Linkages to Other Papers

Edit Linkages Content

Prerequisite(s)

Prerequisite papers: COMP219 or COMPX223

Corequisite(s)

Equivalent(s)

Restriction(s)

Restricted papers: COMP314, COMP315, and COMPX374

Edit Linkages Content